Computing system for identifying, pooling, and managing resources

ABSTRACT

A system may be configured to: receive, from a first user device, resource data associated with a first resource; extract and determine attributes of the first resource and a first user from the resource data; based on the attributes of the first resource and the first user, assign one or more classifications to the first resource and the first user; based on the one or more classifications of the first resource and the first user, predict a future action of the user within a resource management client application; and send, over a network, a future action command to the first user device to prompt the first user to complete the future action.

FIELD OF THE INVENTION

The present invention embraces a computerized system for identifying, pooling, and managing resources. The system is typically configured to: receive, from a first user device, resource data associated with a first resource; extract and determine attributes of the first resource and a first user from the resource data; based on the attributes of the first resource and the first user, assign one or more classifications to the first resource and the first user; based on the one or more classifications of the first resource and the first user, predict a future action of the user within a resource management client application; and send, over a network, a future action command to the first user device to prompt the first user to complete the future action.

BACKGROUND

With the proliferation of Internet technology in recent times, people may utilize online systems to connect with other users or access resources. Conventional methods may include using online website postings to coordinate the users and resources. That said, there are a number of technical problems with using conventional online systems in this manner. In particular, current systems require the users to constantly sift through postings to determine what is relevant and not relevant, thereby leading to inefficiencies of computing resources such as processing power, memory, and network bandwidth.

Accordingly, there is a need for a more efficient and dynamic way to connect users and resources with one another.

BRIEF SUMMARY

The following presents a simplified summary of one or more embodiments of the invention in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments, nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later.

Embodiments of the present invention provide a unique system for identifying, pooling, and managing resources, comprising a resource management server in operative communication with a plurality of user devices of a plurality of users over a network, the plurality of user devices comprising a first user device of a first user; a first processor; a first memory; and a resource management server application stored in the first memory, wherein the resource management server application, when executed by the first processor, causes the first processor to receive, from the first user device, resource data associated with a first resource; extract and determine attributes of the first resource and the first user from the resource data; based on the attributes of the first resource and the first user, assign one or more classifications to the first resource and the first user; based on the one or more classifications of the first resource and the first user, predict a future action of the user within a resource management client application; and send, over the network, a future action command to the first user device to prompt the first user to complete the future action.

In some embodiments, the plurality of user devices comprises a second user device of a second user and a third user device of a third user, wherein the resource management server application, when executed by the first processor, further causes the first processor to identify a subset of users interested in a second resource, the subset of users comprising the second user and the third user; send a resource pooling command to a second plurality of user devices of the subset of users interested in the second resource, wherein the resource pooling command causes the second plurality of user devices to present a resource pooling prompt to the subset of users; detect that the second user and the third user have accepted the resource pooling prompt; create a user group, wherein the user group comprises the second user and the third user; and transfer the second resource to the user group.

In some embodiments, the resource management server application, when executed by the first processor, further causes the first processor to receive authentication credentials from the second user and the third user; query a third party server, wherein the third party server comprises account data associated with the second user and the third user; and receive the account data associated with the second user and the third user from the third party server.

In some embodiments, the resource management server application, when executed by the first processor, further causes the first processor to provide a resource management client application to the first user device, wherein the resource management client applicant, when executed by the first user device, causes the first user device to: display a graphical interface on a display of the first user device; prompt the user to enter authentication credentials to access the resource management server; generate a log of user inputs through the graphical interface; and send the authentication credentials and the log of user inputs to the resource management server.

In some embodiments, the log of user inputs comprises mouse cursor positions, touchscreen inputs, key strokes, or time accessing a particular interface of the resource management client application.

In some embodiments, sending the authentication credentials and the log of user inputs to the resource management server comprises establishing a secure communication link between the first user device and the resource management server.

Embodiments of the present invention also provide a computer program product for identifying, pooling, and managing resources, comprising a non-transitory computer-readable storage medium having computer executable instructions for receiving, from a first user device, resource data associated with a first resource; extracting and determining attributes of the first resource and a first user from the resource data; based on the attributes of the first resource and the first user, assigning one or more classifications to the first resource and the first user; based on the one or more classifications of the first resource and the first user, predicting a future action of the user within a resource management client application; and sending, over the network, a future action command to the first user device to prompt the first user to complete the future action.

In some embodiments, the computer executable instructions further comprise computer-readable program code portions for identifying a subset of users interested in a second resource, the subset of user comprising the second user and the third user; sending a resource pooling command to a second plurality of user devices of the subset of users interested in the second resource, wherein the resource pooling command causes the second plurality of user devices to present a resource pooling prompt to the subset of users; detecting that a second user and a third user have accepted the resource pooling prompt; creating a user group, wherein the user group comprises the second user and the third user; and transferring the second resource to the user group.

In some embodiments, the computer executable instructions further comprise computer-readable program code portions for receiving authentication credentials from the second user and the third user; querying a third party server, wherein the third party server comprises account data associated with the second user and the third user; and receiving the account data associated with the second user and the third user from the third party server.

In some embodiments, the computer executable instructions further comprise computer-readable program code portions for providing the resource management client application to the first user device, wherein the resource management client applicant, when executed by the first user device, causes the first user device to: display a graphical interface on a display of the user device; prompt the user to enter authentication credentials to access the resource management server; generate a log of user inputs through the graphical interface; and send the authentication credentials and the log of user inputs to the resource management server.

In some embodiments, the log of user inputs comprises mouse cursor positions, touchscreen inputs, key strokes, or time accessing a particular interface of the resource management client application.

In some embodiments, sending the authentication credentials and the log of user inputs to the resource management server comprises establishing a secure communication link between the first user device and the resource management server.

Embodiments of the present invention also provide a computer-implemented method for identifying, pooling, and managing resources, said method comprising receiving, from a first user device, resource data associated with a first resource; extracting and determining attributes of the first resource and a first user from the resource data; based on the attributes of the first resource and the first user, assigning one or more classifications to the first resource and the first user; based on the one or more classifications of the first resource and the first user, predicting a future action of the user within a resource management client application; and sending, over the network, a future action command to the first user device to prompt the first user to complete the future action.

In some embodiments, the computer-implemented method further comprises identifying a subset of users interested in a second resource, the subset of users comprising the second user and the third user; sending a resource pooling command to a second plurality of user devices of the subset of users interested in the second resource, wherein the resource pooling command causes the second plurality of user devices to present a resource pooling prompt to the subset of users; detecting that a second user and a third user have accepted the resource pooling prompt; creating a user group, wherein the user group comprises the second user and the third user; and transferring the second resource to the user group.

In some embodiments, the computer-implemented method further comprises receiving authentication credentials from the second user and the third user; querying a third party server, wherein the third party server comprises account data associated with the second user and the third user; and receiving the account data associated with the second user and the third user from the third party server.

In some embodiments, the computer-implemented method further comprises providing the resource management client application to the first user device, wherein the resource management client applicant, when executed by the first user device, causes the first user device to: display a graphical interface on a display of the user device; prompt the user to enter authentication credentials to access the resource management server; generate a log of user inputs through the graphical interface; and send the authentication credentials and the log of user inputs to the resource management server.

In some embodiments, the log of user inputs comprises mouse cursor positions, touchscreen inputs, key strokes, or time accessing a particular interface of the resource management client application.

In some embodiments, sending the authentication credentials and the log of user inputs to the resource management server comprises establishing a secure communication link between the first user device and the resource management server.

The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, wherein:

FIG. 1 depicts an operating environment, in accordance with one embodiment of the present invention;

FIG. 2 depicts a schematic of a user device and a resource management server, in accordance with one embodiment of the present invention;

FIG. 3 depicts a process flow for identifying and managing resources according to user and resource classifications, in accordance with one embodiment of the present invention; and

FIG. 4 depicts a process flow for pooling and managing resources according to defined user groups, in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to elements throughout. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein.

“User” as used herein may refer to an individual or entity that utilizes a system for identifying, pooling, and managing resources as described herein. In some embodiments, the user may be a representative of a business entity. In other embodiments, the user may be an independent contractor who is looking to offer a resource to other users in the system. For instance, a user may be a participant who wishes to offer services and goods to the other users within the system. To this end, another the user may be a participant who wishes to obtain services or goods from the users within the system. In this way, the system connects users together so that they may efficiently exchanges resources with one another.

“Entity” as used herein may refer to an individual or an organization that owns and/or operates the resource management systems and the associated computing systems. The entity may be a business organization, a non-profit organization, a government organization, and the like.

“User device” as used herein may refer to a computing device used by the user to access the system through an online portal. The user device may include a processor, a non-transitory storage medium, a communications device, and a display. The system may support user logins and inputs from any combination of disparate devices. Accordingly, the user device may be a portable electronic device such as a smartphone, tablet, or laptop, or the user device may be a stationary unit such as a personal desktop computer or a networked terminal within an entity's premises.

“Resource” as used herein may refer to a property of the user over which the user exercises control, or an asset belonging to the user. For instance, a resource may refer to a particular good or service which the user may wish to provide to or obtain from other users. The resource may further refer to intangible assets, such as a user's credentials.

“Resource data” as used herein may refer to a data structure that is associated with a particular resource. Resource data is identified, manipulated, or classified by the system, and may include various types of information upon which the system performs its various functions. In some embodiments, the information may include an offer to sell goods or services. In other embodiments, the information may include a request for goods or services. The information may further include location data, pricing data, or time data. The information may further include an identity of a user or various characteristics or statistics of the user.

“Classification” as used herein refers to a status attributed to resource data by the system in order to provide for organization or grouping of the resources. In some embodiments, resources may be classified by “likeness,” or by certain similar characteristics inherent to the resource. In some embodiments, resources may also be classified according to links established by the system's user base, independently of the “likeness” of the resources within such a classification. In this way, the system may intelligently provide recommendations of resources to the user even if the relevance of such resources to the user is not immediately evident. Classifications for resources may be stored in a classifications database, and may include a unique fixed-length string to identify the classification. The fixed-length string may be a numerical value such as “8251,” a cryptographic hash, or a plain-text description of the classification, such as “Linux drivers.”

Embodiments of the present invention provide a system for identifying and pooling resources, as well as tools that enable users to manage the pooled resources. In particular, the system may identify resource data provided by an authenticated user and assign a classification to the resource based on the data type. The system may further create logical links between and amongst the resources provided by all authenticated users within the system according to their respective classifications, grouping like resources or related resources together. Resources may be assigned to one or more classifications and may be “tagged” for later identification and retrieval by the system based on the data contained within the resources. For example, the system may classify resources according to various criteria, such as data file types, key words or phrases, upload date, geographic restrictions, and the like. The system may then provide the aggregated data to the user for further processing and input. In some embodiments, the classifications for particular resources and logical links between particular resources may be stored in a classifications database. The system may further provide classifications for users based on the types of resource data they upload or access. For instance, a user may be classified according to certain criteria, such as skillsets, geographic location, areas of expertise/profession, and the like. In this way, the system may build a profile of a user based on the user's numerous classifications, and accordingly recommend certain resources according to the logical links created amongst the user and the resources.

The system may include a data collection module which tracks inputs from users on a real-time basis, where the inputs may be resource data or requests for resources. In some embodiments, the system may further include a data analytics engine that, based on both historical data and data provided by the users in real time, predicts future subsequent actions or inputs by the user based on the resource data provided by the user or actions taken by the user, and provide suggestions of potential resources or portal tools of interest to the user. Such historical data may be stored on a long-term basis in a user input database. By calculating predictions and providing resource or tool suggestions, the system prevents the need for the user to manually seek out resources related to one's interest. For instance, in one embodiment of the invention, a user may upload a file including a sample of source code to the system. The system may detect that the file includes source code, and based on the contents of the source code therein, the system may make a number of recommendations to the user. The system may make this determination, for example, by reading the contents of the source code, such as the types of functions used, the programming language used, and the software libraries incorporated within the code. In response, the system may provide a listing of additional project opportunities that may be suitable to the user. The system may also provide a list of users within the system who could serve as collaborators on a given coding project, which the system identifies by detecting that the users have worked on similar projects in the past. In other embodiments, a user may upload a posting to provide goods or services, where the posting includes data of various file types and may include images, videos, text, and the like. The system may characterize the data within the posting by analyzing it for image or video metadata, or keywords. Based on this analysis, the system may then dynamically provide the user with a number of suggestions for resources that are related to the posting, which may include other users who are potentially interested in the good or service offered, or a suggestion to purchase a material that is necessary to provide the service. In some embodiments, the system may provide rewards to users who exchange resources to other users through the system. In some embodiments, the system may analyze user data (e.g., historic transaction data) to assess the likelihood that a particular user may be unable to or otherwise fail to pay for resources purchased through the system, deliver resources purchased by others through the system, deliver satisfactory resources, and the like. This information may be provided to other users of the system. In addition, the system may guarantee a user payment from another user through the system (e.g., to purchase goods or services from the user) and/or the delivery or quality of a resource purchased through the system. Accordingly, in the event the user does not receive a payment or a resource or the quality of a resource is deficient, the system may compensate the user.

In some embodiments, the system may include an online portal which serves as the interface between the system and the users. The system may run its processes on a server or network of servers which users may access using a computing device. In some embodiments, the system may provide to the user a client application or program which is used to access the server-side application over a network. The online portal may present a graphical interface to the display of the user device, through which the user may select from a number of tools and functions provided by the system. For instance, the system may provide tools to pool resources with or amongst users within the system.

The graphical interface may include a number of panels which may receive inputs or display information to the user. For example, the graphical interface may include a resource input panel, which allows the user to upload resource data into the system. The resource input panel may contain buttons or areas that receive user input related to the resources, such as a text entry box, or a sub-panel through which the user may upload various media files to the system. The graphical interface may further include a resource listing panel, which contains a list of resources sorted by its classification. The resource listing panel may also contain various filters to allow the user to change the number and order of resources listed on the screen at once according to certain criteria, such as upload date, classification, resource contents, popularity, and the like. In this way, the resource listing panel allows the user to effectively browse through the resources uploaded to the system.

The graphical interface may also include a notifications panel, through which the system provides resource recommendations to the user. The resource recommendations displayed in the notifications panel may further contain a selectable link which the user may use to directly access the suggested resource. In some embodiments, the graphical interface may include a resource information panel, which provides a user with statistical data about a selected resource by comparing the user-inputted resource data with like resources data provided by other users within the system. For example, the user may upload a posting to provide a particular good for a particular price. The system may recognize that the posting includes an offer to provide a particular good, identify the classification of the particular good, and retrieve statistical pricing data for the particular good. The system may then provide this data to the user through the resource information panel, and may further provide a pricing suggestion for the good to be provided.

In some embodiments, the system may dynamically track usage data through the resource management application on the user device. In particular, the resource management application may track user inputs, such as mouse cursor positions, touchscreen inputs, key strokes, and the like. The system may establish a secure communication channel with the resource management application or other client application on the user device in order to obtain real-time usage data of the user's actions within the application. Based on these user inputs as well as historical data and the user's attributes/classification(s) (and attributes/classification(s) of resources of the user), the system may predict future actions that the user intends to take (e.g., within a client application) and make recommendations according to the predictions. For instance, the system may track the length of time and level of activity with which the user spends viewing data relating to a particular resource. In such an embodiment, the system may gauge the duration that a user spends viewing a posting for a good or service, and track whether the user has opened any attachments associated with the posting, such as images or videos. In this way, the system may estimate the level of interest in a particular resource by a particular user and assign a “relevance score” to the classification of the particular resource. The system will consider higher relevance scores to represent resources that are more relevant to a user. Subsequently, the system may then provide a list of potentially relevant resources in the notifications panel, which may be populated with references sorted by their relevance score or classification, e.g. users of classification A are typically interested in resources of classifications B, C, and D.

In some embodiments, rather than or in addition to providing suggestions, the data analytics engine may, based on tracking a user's inputs, the user's attributes, historical data, and the like, dynamically predict subsequent actions that the user intends to take within the graphical interface or otherwise when interacting with the resource management system. Thereafter, the system may transmit a command to a client application on the user's device that causes the application to display an interface for performing the predicted future action. For example, the system may have stored historical data which shows that a user requests access to a particular resource when the user logs onto the system in regular time intervals. Upon detecting that the user has logged on, that the calculated time period has passed, and the user has not yet requested the particular resource, the system may automatically prompt the user to access the particular resource. In this way, the system allows the user to bypass the manual extraneous steps to access the particular resource, thereby improving the computing efficiency of the servers on which the system is implemented.

The system may further establish relevance scores or classifications for a resource based on the resource's use by users in the system. For instance, the system may track the number of times one resource is linked to or accessed by another resource. The system may further track the number of times a resource was accessed through the recommendations panel. In this way, the system may intelligently increase the relevant scores for resource combinations/suggestions even if such combinations of classifications were not predefined by the system or its administrators. In other words, the system may dynamically adjust its recommendations system to account for unusual or unexpected resource pairings or changes in trends regarding the resources amongst the system's users.

In some embodiments, the system may be owned or operated by an entity. In such embodiments, the entity may employ additional computer systems, such as authentication servers, to validate and certify resources inputted by the plurality of users within the system. The system may further use its authentication servers to certify the identity of users of the system, such that other users may verify the identity of the certified users. In some embodiments, the entity may certify the identity of the users.

The system addresses a number of computer technology-centric challenges as described above. As noted, the system is typically configured to dynamically predict future actions that a user intends to take (e.g., within a client application on the user's device that interacts with the resource management system) by monitoring a user's inputs, attributes, historical data, and the like. By dynamically predicting future actions, the system is then able to prompt the user to complete the predicted action, while avoiding intermediate interactions that the system would have otherwise had with the user. By avoiding these intermediate interactions, the system is able to reduce demands on computer resources. In addition, by dynamically identifying and pooling like data, the system improves the efficiency of the online system by reducing the incidence of wasted computing resources caused by manual searching of relevant resources by the users. In other words, by automatically providing suggestions for resources based on their identified data classification, the system removes the need for the user to strain the system's servers by manually sifting through irrelevant data. Instead, the system intelligently provides the relevant data to the user before such manual searching takes place, thereby increasing computing efficiency. The types of computing resources saved by the foregoing may include, but are not limited to, processing power, memory space, storage space, cache space, electric power, and networking bandwidth.

FIG. 1 is a block diagram illustrating an operating environment 001, in accordance with one embodiment of the present invention. The operating environment may include a plurality of user devices 100 in operative communication with a resource management server 101 over a network 180. The network 180 may also be a global area network (GAN), such as the Internet, a wide area network (WAN), a local area network (LAN), or any other type of network or combination of networks. The network 180 may provide for wireline, wireless, or a combination wireline and wireless communication between devices on the network 180. The user device may be a mobile device such as a smartphone, tablet, or laptop, a personal computing device such as a desktop computer, smart device, single board computer, or a device owned and operated by an entity, such as a computer system terminal located on the entity's premises. The resource management server 101 is responsible for running the resource management application and running its various processes. It should be understood that the resource management server 101 as depicted herein may be embodied in a single server or multiple servers distributed over varying geographic distances.

Generally, the user devices 100 are used to log onto the resource management server 101 over the network 180 to access the online portal (e.g., over a secure communication channel). The resource management server 101 may require that authentication credentials are provided by the user device 100. In some embodiments, the authentication credentials may include a username, password, a biometric identifier, a cryptographic key, a token, and the like. The resource management server 101 may further require that more than one authentication credential is provided as parts of a multi-step authentication process. Once the user has been authenticated, the user may log onto the online portal on the resource management server 101 using the user device 100 to access the resources and resource management tools therein.

In some embodiments, the operating environment may further include a third party server 102 which may be in operative communication with the user device 100, the resource management server 101, or both, over the network 180. The third party server 102 may contain data associated with the user which may be accessed by some of the resource management tools run on the resource management server 101. This configuration allows the resource management server 101 to automatically pull the data associated with the user from the third party server 102 in order to run its various processes. For example, the third party server 102 may contain data relating to the user's financial accounts, and the resource management server 101 may provide tools to manage that data. In such an embodiment, the user may provide a second set of authentication credentials associated with the user's financial account to the third party server 102 directly. Alternatively, the user may store the second set of authentication credentials on the resource management server 101, which may then use said authentication credentials to access the data within the third party server 102.

FIG. 2 is a block diagram illustrating the resource management server 101 and the user device 100 in more detail, in accordance with one embodiment of the present invention. The resource management server 101 typically contains a processor 120 communicably coupled to such devices as a communication interface 110 and a memory 130. The processor 120, and other processors described herein, typically includes circuitry for implementing communication and/or logic functions of the server 101. For example, the processor 120 may include a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and/or other support circuits.

The resource management server may use the communication interface 110 to communicate with other devices over the network 180. The communication interface 110 as used herein may include an Ethernet interface, an antenna coupled to a transceiver configured to operate on a cellular data or WiFi signal, and/or a near field communication (“NFC”) interface.

The resource management server may include a memory 130 operatively coupled to the processor 120. As used herein, memory includes any computer readable medium (as defined herein below) configured to store data, code, or other information. The memory may include volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The memory may also include non-volatile memory, which can be embedded and/or may be removable. The non-volatile memory can additionally or alternatively include an electrically erasable programmable read-only memory (EEPROM), flash memory or the like.

Typically, a resource management server application 150 is stored within the memory 130 to implement the functions of the online portal through the processor 120 on the resource management server 101. The resource management server application 150 allows a user 170 to connect to the resource management server 101 through a user device 100, in order to access the resource data therein as well as utilize the resource management tools provided through the online portal. The resource management server application 150 includes the logic code portions to determine the appropriate resource recommendations as well as the code portions to collect usage and historical data from the plurality of users 170 within the system.

The memory 130 may further include a database 140 containing data to be processed and/or manipulated by the resource management server application 150. The database 140 may contain usage and historical data provide by the users 170. The database 140 may also contain data on the various classifications to be used to categorize the resources and the users, on what classifications correspond to which resources, as well as logical links between and amongst the various resources and the users. It should be understood that while the database 140 is depicted as a single unit within a single resource management server in FIG. 3, the database 140 may represent multiple databases implemented across multiple resource management servers 101. It should also be understood that the resource management server application 150 may implemented in a distributed manner amongst a plurality resource management servers 101. The database 140 may also be stored on a separate, distinct memory 130 from the resource management server application 150.

The user device 100 typically also includes a processor 121 operatively coupled to a communication interface 111 and a memory 131. The memory 131 typically stores a resource management client application 151, which causes the processor 121 to display a user interface 160 to the user 170. It should be understood that the display on which the user interface 160 is presented may include an integrated display (e.g. a tablet or smartphone screen) within the user device 100, or an external display device (e.g. a computer monitor or television). The resource management client application 151 establishes a connection with the resource management server application 150 over the network 180 to allow the user 170 to access the various functions of the system. In particular, the resource management client application 151 receives inputs from the user interface 160, which may include such inputs as user authentication credentials, requests to upload resource data, which may include various types of data such as activity data, to the resource management server 101, requests to utilize the resource management tools of the resource management server application 150, and the like.

In a typical embodiment of the invention, the user 170 accesses the resource management client application 151 through the user interface 160. The resource management client application 151 sends a request over the network 180 to establish a communication link with the resource management server 101 through the resource management server application 150. Upon receiving the request, the resource management server application 150 causes the resource management server 101 to send a command to the user device 100 to prompt the user 170 for authentication credentials through the user interface 160. Upon receiving authentication credentials from the user 170, the resource management client application 151 sends the authentication credentials to the resource management server application 150. Upon successful authentication, a communication link between the resource management client application 151 and the resource management server application 150 is established. The user 170 then provides a request to upload resource data to the resource management client application 151, which then sends the resource data to the resource management server application 150. The resource management server application 150 then processes the contents of the resource data, and based on a combination of user inputs, historical data within the database 140, and various types of data found within the resource data, adds classifications or tags to the user 170 and/or the resource data provided by the user. The resource management server application 150 then predicts future actions that the user 170 intends to take within the user interface 160, and prompts the user through a notification to take the intended future action.

The system may store user activity data within the online portal within the database 140. In some embodiments, the resource management server application 150 may cause the processor 120 to periodically query the user device 100 to obtain snapshots of the state of the resource management client application 151. Upon receiving the query, the resource management client application 151 immediately obtain a snapshot of user actions taken within the graphical interface, then send the snapshot to the resource management server 101. In other embodiments, the resource management client application 151 may continuously track user inputs and temporarily store them in the memory 131, then send the history of user inputs to the resource management server 101 upon receiving the query. In other embodiments, the resource management client application 151 may periodically track the user's inputs and push the input data to the resource management server 101 without waiting to receive a query.

FIG. 3 illustrates a process flow 003 for identifying and managing resources according to user and resource classifications, in accordance with one embodiment of the present invention. The process begins at block 300, wherein the resource management server application 150 receives the resource data from the user device. In some embodiments, the resource data may include an offer to provide a resource, such as a good or service. In other embodiments, the resource data may include a request seeking a particular resource. In yet other embodiments, the resource data may include a proposal to seek a particular resource amongst a group of users within the resource management system. In some embodiments, the resource management server application 150 may additionally require successful verification of authentication credentials before accepting the resource data. The authentication credentials may be associated with an account of the user on the resource management entity server. The account may contain information and statistics about the user, and may include personal information and system usage information.

The process continues to block 301, where attributes of the resource and of the user are extracted and determined from the resource data. The resource management server application 150 may determine attributes of the resource by extracting file information from the resource data, such as text, image, or video data. The resource management server application 150 may determine attributes of the user by extracting information from the account of the user, and/or by analyzing historical data of how the user has used the resource management system in the past.

The process continues to block 302, where one or more classifications are assigned to the resource and the user based on the attributes of the resource and the user. In some embodiments, the system may assign classifications to the resource by tagging the resource data with the classifications. Similarly, in some embodiments, the system may assign classifications to the user by tagging the account of the user with the classifications. The system may further create logical links between resources and/or users by calculating the frequency by which users having particular classifications upload resource data associated with resources having particular classifications. In addition, the system may link users and/or resources having similar attributes and/or classifications.

The process continues to block 303, where a future action of the user (e.g., an action of the user in a client application) is predicted based on the one or more classifications of the resource and the user. In some embodiments, the system may base the prediction on the logical links between classifications of the resource and/or the user, and/or a real-time or near real-time snapshot of the user's inputs on the user device. Depending on the attributes of the user, the system may temporarily decline to allow the user to take future actions. For instance, if the user's account with the entity is not in good standing, the system may temporarily block the user from requesting resources and/or uploading resource data.

Finally, the process concludes at block 304, where a future action command is sent, over a network, to the user device to prompt the user to complete the future action. The command to the user device may cause the user device to notify the user of a future action through a prompt or pop-up within the graphical interface on the display of the user device. The prompt may include a button or link to automatically complete the future action. In some embodiments, if the future action is a request for a resource provided by another user within the system, the system may provide a reward or incentive for requesting the resource through the system.

FIG. 4 illustrates a process flow 004 for pooling and managing resources according to defined user groups, according to one embodiment of the present invention. The process begins at block 400, in which the resource management server application 150 identifies a plurality of users 170 interested in a particular resource. In some embodiments, the users may be identified using user inputs, historical data, resource classifications, and user classifications to predict that the user 170 intends to request a particular resource or otherwise has an interested in requesting the particular resource. The particular resource may be a resource owned by one or more the users within the resource management system. In other embodiments, the resource may be a good or service provided by a third party which is suitable to be shared amongst a plurality of users.

The process continues to block 401, where a resource pooling command is sent to the user device of each user that may be interested in the resource. The resource pooling command is typically configured to cause each user device to present a resource pooling prompt to the user of the device. The resource pooling prompt may be displayed on the user device and prompt the user to accept or decline the proposed resource pooling. In some embodiments, the prompt may appear as a notification within the notifications panel of the graphical user interface. The prompt may alternatively appear in a push notification or pop-up within the user interface 160.

The process continues to block 402, where one or more users are detected to have accepted the resource pooling prompt. In some embodiments, the detection is based on a user providing an affirmative input to that user's device. In some embodiments, the system may wait to receive either an affirmative or negative input from all prompted users before proceeding with its next steps. In other embodiments, the system may proceed after a “timeout” period has expired, wherein the timeout represents the minimum time the system waits before proceeding to the next step, i.e. the time allotment during which the user must accept or reject the prompt.

The process continues to block 403, where a user group containing each user that accepted the prompt is created. The system may group the responsive users according to their respective resource needs.

The process concludes at block 404, where the resource is transferred to the user group. The system may arrange for the transfer of the resource automatically. In the event that the resource is owned or provided by a particular user, the system may send a notification to the user to provide the resource to the user group. In the event that the resource is owned or provided by a third party, the system may send a notification to the third party or establish a communication link with a third party server to furnish the resource to the user group.

Each communication interface described herein generally includes hardware, and, in some instances, software, that enables the computer system, to transport, send, receive, and/or otherwise communicate information to and/or from the communication interface of one or more other systems on the network. For example, the communication interface of the user input system may include a wireless transceiver, modem, server, electrical connection, and/or other electronic device that operatively connects the user input system to another system. The wireless transceiver may include a radio circuit to enable wireless transmission and reception of information.

As will be appreciated by one of ordinary skill in the art, the present invention may be embodied as an apparatus (including, for example, a system, a machine, a device, a computer program product, and/or the like), as a method (including, for example, a business process, a computer-implemented process, and/or the like), or as any combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely software embodiment (including firmware, resident software, micro-code, and the like), an entirely hardware embodiment, or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product that includes a computer-readable storage medium having computer-executable program code portions stored therein.

As the phrase is used herein, a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function.

It will be understood that any suitable computer-readable medium may be utilized. The computer-readable medium may include, but is not limited to, a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, infrared, electromagnetic, and/or semiconductor system, apparatus, and/or device. For example, in some embodiments, the non-transitory computer-readable medium includes a tangible medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), and/or some other tangible optical and/or magnetic storage device. In other embodiments of the present invention, however, the computer-readable medium may be transitory, such as a propagation signal including computer-executable program code portions embodied therein.

It will also be understood that one or more computer-executable program code portions for carrying out the specialized operations of the present invention may be required on the specialized computer include object-oriented, scripted, and/or unscripted programming languages, such as, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, and/or the like. In some embodiments, the one or more computer-executable program code portions for carrying out operations of embodiments of the present invention are written in conventional procedural programming languages, such as the “C” programming languages and/or similar programming languages. The computer program code may alternatively or additionally be written in one or more multi-paradigm programming languages, such as, for example, F#.

Embodiments of the present invention are described above with reference to flowcharts and/or block diagrams. It will be understood that steps of the processes described herein may be performed in orders different than those illustrated in the flowcharts. In other words, the processes represented by the blocks of a flowchart may, in some embodiments, be in performed in an order other that the order illustrated, may be combined or divided, or may be performed simultaneously. It will also be understood that the blocks of the block diagrams illustrated, in some embodiments, merely conceptual delineations between systems and one or more of the systems illustrated by a block in the block diagrams may be combined or share hardware and/or software with another one or more of the systems illustrated by a block in the block diagrams. Likewise, a device, system, apparatus, and/or the like may be made up of one or more devices, systems, apparatuses, and/or the like. For example, where a processor is illustrated or described herein, the processor may be made up of a plurality of microprocessors or other processing devices which may or may not be coupled to one another. Likewise, where a memory is illustrated or described herein, the memory may be made up of a plurality of memory devices which may or may not be coupled to one another.

It will also be understood that the one or more computer-executable program code portions may be stored in a transitory or non-transitory computer-readable medium (e.g., a memory, and the like) that can direct a computer and/or other programmable data processing apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture, including instruction mechanisms which implement the steps and/or functions specified in the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus. In some embodiments, this produces a computer-implemented process such that the one or more computer-executable program code portions which execute on the computer and/or other programmable apparatus provide operational steps to implement the steps specified in the flowchart(s) and/or the functions specified in the block diagram block(s). Alternatively, computer-implemented steps may be combined with operator and/or human-implemented steps in order to carry out an embodiment of the present invention.

While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.

INCORPORATION BY REFERENCE

To supplement the present disclosure, this application further incorporates entirely by reference the following commonly assigned patent applications:

U.S. patent application Docket Number Ser. No. Title Filed On 7605US1.014033.2948 To be assigned COMPUTERIZED SYSTEM FOR Concurrently IDENTIFYING AND herewith REDISTRIBUTING COMPLEMENTARY RESOURCES 7607US1.014033.2950 To be assigned SYSTEM FOR IDENTIFICATION Concurrently AND INTEGRATION OF LIKE herewith RESOURCES AND CONFIGURING RESOURCES FOR COMMON USE 7608US1.014033.2951 To be assigned SYSTEM FOR DYNAMICALLY Concurrently MANAGING RESOURCE herewith CONNECTIVITY 

What is claimed is:
 1. A system for identifying, pooling, and managing resources, comprising: a resource management server in operative communication with a plurality of user devices of a plurality of users over a network, the plurality of user devices comprising a first user device of a first user; a first processor; a first memory; and a resource management server application stored in the first memory, wherein the resource management server application, when executed by the first processor, causes the first processor to: receive, from the first user device, resource data associated with a first resource; extract and determine attributes of the first resource and the first user from the resource data; based on the attributes of the first resource and the first user, assign one or more classifications to the first resource and the first user; based on the one or more classifications of the first resource and the first user, predict a future action of the user within a resource management client application; and send, over the network, a future action command to the first user device to prompt the first user to complete the future action.
 2. The system of claim 1, wherein the plurality of user devices comprises a second user device of a second user and a third user device of a third user, wherein the resource management server application, when executed by the first processor, further causes the first processor to: identify a subset of users interested in a second resource, the subset of users comprising the second user and the third user; send a resource pooling command to a second plurality of user devices of the subset of users interested in the second resource, wherein the resource pooling command causes the second plurality of user devices to present a resource pooling prompt to the subset of users; detect that the second user and the third user have accepted the resource pooling prompt; create a user group, wherein the user group comprises the second user and the third user; and transfer the second resource to the user group.
 3. The system of claim 2, wherein the resource management server application, when executed by the first processor, further causes the first processor to: receive authentication credentials from the second user and the third user; query a third party server, wherein the third party server comprises account data associated with the second user and the third user; and receive the account data associated with the second user and the third user from the third party server.
 4. The system of claim 1, wherein the resource management server application, when executed by the first processor, further causes the first processor to: provide the resource management client application to the first user device, wherein the resource management client applicant, when executed by the first user device, causes the first user device to: display a graphical interface on a display of the first user device; prompt the user to enter authentication credentials to access the resource management server; generate a log of user inputs through the graphical interface; and send the authentication credentials and the log of user inputs to the resource management server.
 5. The system of claim 4, wherein the log of user inputs comprises mouse cursor positions, touchscreen inputs, key strokes, or time accessing a particular interface of the resource management client application.
 6. The system of claim 4, wherein sending the authentication credentials and the log of user inputs to the resource management server comprises establishing a secure communication link between the first user device and the resource management server.
 7. A computer program product for identifying, pooling, and managing resources, comprising a non-transitory computer-readable storage medium having computer executable instructions for: receiving, from a first user device, resource data associated with a first resource; extracting and determining attributes of the first resource and a first user from the resource data; based on the attributes of the first resource and the first user, assigning one or more classifications to the first resource and the first user; based on the one or more classifications of the first resource and the first user, predicting a future action of the user within a resource management client application; and sending, over a network, a future action command to the first user device to prompt the first user to complete the future action.
 8. The computer program product of claim 7, wherein the computer executable instructions further comprise computer-readable program code portions for: identifying a subset of users interested in a second resource, the subset of users comprising the second user and the third user; sending a resource pooling command to a second plurality of user devices of the subset of users interested in the second resource, wherein the resource pooling command causes the second plurality of user devices to present a resource pooling prompt to the subset of users; detecting that a second user and a third user have accepted the resource pooling prompt; creating a user group, wherein the user group comprises the second user and the third user; and transferring the second resource to the user group.
 9. The computer program product of claim 8, wherein the computer executable instructions further comprise computer-readable program code portions for: receiving authentication credentials from the second user and the third user; querying a third party server, wherein the third party server comprises account data associated with the second user and the third user; and receiving the account data associated with the second user and the third user from the third party server.
 10. The computer program product of claim 7, wherein the computer executable instructions further comprise computer-readable program code portions for providing the resource management client application to the first user device, wherein the resource management client applicant, when executed by the first user device, causes the first user device to: display a graphical interface on a display of the user device; prompt the user to enter authentication credentials to access a resource management server; generate a log of user inputs through the graphical interface; and send the authentication credentials and the log of user inputs to the resource management server.
 11. The computer program product of claim 10, wherein the log of user inputs comprises mouse cursor positions, touchscreen inputs, key strokes, or time accessing a particular interface of the resource management client application.
 12. The computer program product of claim 10, wherein sending the authentication credentials and the log of user inputs to the resource management server comprises establishing a secure communication link between the first user device and the resource management server.
 13. A computer-implemented method for identifying, pooling, and managing resources, said method comprising: receiving, from a first user device, resource data associated with a first resource; extracting and determining attributes of the first resource and a first user from the resource data; based on the attributes of the first resource and the first user, assigning one or more classifications to the first resource and the first user; based on the one or more classifications of the first resource and the first user, predicting a future action of the user within a resource management client application; and sending, over a network, a future action command to the first user device to prompt the first user to complete the future action.
 14. The computer-implemented method of claim 13, further comprising: identifying a subset of users interested in a second resource, the subset of users comprising the second user and the third user; sending a resource pooling command to a second plurality of user devices of the subset of users interested in the second resource, wherein the resource pooling command causes the second plurality of user devices to present a resource pooling prompt to the subset of users; detecting that a second user and a third user have accepted the resource pooling prompt; creating a user group, wherein the user group comprises the second user and the third user; and transferring the second resource to the user group.
 15. The computer-implemented method of claim 14, further comprising: receiving authentication credentials from the second user and the third user; querying a third party server, wherein the third party server comprises account data associated with the second user and the third user; and receiving the account data associated with the second user and the third user from the third party server.
 16. The computer-implemented method of claim 13, further comprising providing the resource management client application to the first user device, wherein the resource management client applicant, when executed by the first user device, causes the first user device to: display a graphical interface on a display of the first user device; prompt the user to enter authentication credentials to access a resource management server; generate a log of user inputs through the graphical interface; and send the authentication credentials and the log of user inputs to the resource management server.
 17. The computer-implemented method of claim 16, wherein the log of user inputs comprises mouse cursor positions, touchscreen inputs, key strokes, or time accessing a particular interface of the resource management client application.
 18. The computer-implemented method of claim 16, wherein sending the authentication credentials and the log of user inputs to the resource management server comprises establishing a secure communication link between the first user device and the resource management server. 